style: Fix invalid-escape-sequence (W605) #4409
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
raster
These tests were part of Google code-in and some of them shouldn't have been merged... I suggest to completely remove the |
petrasovaa
approved these changes
Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ruff rule: https://docs.astral.sh/ruff/rules/invalid-escape-sequence/
Even though it fixes the invalid escape sequence, I still think that these stings are wrong, or don't do what we expect them to do.
For example, I would expect the string INPUT_TSV to have tabs, but there aren't, nor at the first commit of that file 7 years ago in 007fe9c.
The backslashes needed in imagery/i.pca/testsuite/test_pca.py seem weird to me too, as wouldn't there be some newlines somewhere?